Definition

A System Refresh is a system that was already logo'd using a previous design guide that is re-tested so that it can maintain its existing logo but ship with certain types of component updates. Refreshed systems are tested according to the guidelines of the design guide that they were originally logo'd with, however, they must be tested with current Hardware Compatibility Test kits (HCTs).

Timeline

PC 97 Refreshes

• Currently, WHQL is accepting refreshes of systems logo'd under the PC 97 guidelines.
• PC 97 non-server refreshes will no longer be accepted after 1/1/2000.

PC 98 Refreshes

• WHQL will begin accepting refreshes of systems logo'd under the PC 98 guidelines beginning July 1, 1999.
• PC 98 refreshes will no longer be accepted after July 1, 2001.
• As of July 1, 1999, submissions of newly created systems designed according to the guidelines in the PC 98 System Design Guide will no longer be accepted.

Server Refreshes

NOTE: Server system designs can be refreshed through two Hardware Design Guide for Microsoft Windows NT® Server releases.

• WHQL will begin accepting refreshes of systems logo'd under the SDG 1.0 guidelines beginning July 1, 1999.
• SDG 1.0 refreshes will be accepted through the SDG 3.0 timeframe, until date that has yet to be determined.
• As of July 1, 1999, submissions of newly created systems designed according to the guidelines laid down in the Hardware Design Guide Version 1.0 for Microsoft Windows NT® Server will no longer be accepted.

Rules

• Re-test with current HCTs: System Refreshes must be tested with currently released Hardware Compatibility Test Kits. Failures due to requirements or tests that are new since the HCT that the system was originally tested with will be waived. Current kits must be used because WHQL has added new test coverage to the HCTs, and it benefits OEMs to be aware of this added coverage, to expose issues with hardware and drivers, and to understand new requirements, even if these requirements will not affect this particular submission.
• BIOS changes: Minor BIOS changes since the original logo'd submission, such as timing issues, are allowed. BIOS changes that alter fundamental ACPI, Plug and Play, or power management functionality disqualify a system from participating in the system refresh program. Systems with significant BIOS changes must be submitted as new systems and tested under the current guidelines to become logo'd.
• CPU upgrades: NEW CPUs must be pin compatible with the CPU used in the originally logo'd system. Architecture and/or CPU manufacturer changes will disqualify a system from participating in the system refresh program. Systems with architecture and/or CPU manufacturer changes must be submitted as new systems and tested under the current guidelines to become logo'd.
• Component Changes:
  • Add-in components: New logo'd Add-in components may be added to logo'd systems without the need for a refresh submission.
  • Onboard components: New components must pass WHQL testing and meet the current specification at the time of the system refresh. New components must be pin compatible with the original component and must be from the same manufacturer as the original component.
• For Mobile Systems Only:
  • Display: TFT display size changes on mobile systems are allowed.
  • Docking Stations: New docking stations for mobiles must meet the current specification at the time of the refresh
• Model Name Changes: Minor model name changes are allowed. Model name changes must indicate that the refreshed system is an update or later version of the originally logo'd model, by adding a higher number to the model name, for example . Model name changes that imply that the refreshed system is a new design are not allowed. For example, model name changes such as "Supersystem 133" to "Supersystem 200" are allowed, but changes such as "Supersystem 133" to "ProSystem 200" are not allowed.